Apparatuses, methods and systems for an  eventual event calendaring platform

ABSTRACT

The APPARATUSES, METHODS AND SYSTEMS FOR AN EVENTUAL EVENT CALENDARING PLATFORM (hereinafter “EECP”) transforms inputs (e.g., user information, user profile information, event information, import calendar information, etc.) via components (e.g., Event Retrieval Component, Event Collection Component, Event Assignment Component, Eventually Button, Event Collection and Scoring Component, Event Calendaring Component, etc.) into outputs (e.g., user calendar, user calendar RSS feed, user profile, etc.). The EECP provides dynamic, management, analysis, and control of event information and relationships. In one embodiment, the EECP may be configured to provide a user with a calendar implementation that may be populated with events based on the user&#39;s identified interests, preferences and historical activity.

RELATED APPLICATIONS

This application claims priority under 35 USC § 119 to U.S. provisionalpatent application Ser. No. 61/386,440 filed Sep. 24, 2010, entitled“APPARATUSES, METHODS AND SYSTEMS FOR AN EVENTUAL EVENT CALENDERINGPLATFORM,” attorney docket no. 17209-003PV. The entire contents of theaforementioned application are herein expressly incorporated byreference.

This application for letters patent disclosure document describesinventive aspects directed at various novel innovations (hereinafter“disclosure”) and contains material that is subject to copyright, maskwork, and/or other intellectual property protection. The respectiveowners of such intellectual property have no objection to the facsimilereproduction of the disclosure by anyone as it appears in publishedPatent Office file/records, but otherwise reserve all rights.

FIELD

The present invention is directed generally to an apparatuses, methods,and systems for generating event and activity relationships, and moreparticularly, to APPARATUSES, METHODS AND SYSTEMS FOR AN EVENTUAL EVENTCALENDARING PLATFORM.

BACKGROUND

Activities take place everyday, at various times, in various locations,and host various people. People use tools like calendars to plan andprepare for activities.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying appendices and/or drawings illustrate variousnon-limiting, example, inventive aspects in accordance with the presentdisclosure:

FIG. 1 shows a data flow diagram illustrating example aspects of someembodiments of the EECP;

FIG. 2 is a logic flow diagram illustrating an embodiment of the EECP.

FIG. 3 is a logic flow diagram illustrating an embodiment of the EECP;and

FIG. 4 is of a block diagram illustrating embodiments of the EECPcontroller.

The leading number of each reference number within the drawingsindicates the figure in which that reference number is introduced and/ordetailed. As such, a detailed discussion of reference number lot wouldbe found and/or introduced in FIG. 1. Reference number 201 is introducedin FIG. 2, etc.

DETAILED DESCRIPTION EECP

This disclosure details APPARATUSES, METHODS AND SYSTEMS FOR AN EVENTUALEVENT CALENDARING PLATFORM (hereinafter “EECP”) that transforms inputs(e.g., user information, user profile information, event information,import calendar information, etc.) via components (e.g., Event RetrievalComponent, Event Collection Component, Even Assignment Component,Eventually Button, Event Collection & Scoring Component, EventCalendaring Component, etc.) into outputs (e.g., user calendar, usercalendar RSS feed, user profile, etc.). The EECP provides dynamic,management, analysis, and control of event information andrelationships. In one embodiment, the EECP may be configured to providea user with a calendar implementation that may be populated with eventsbased on the user's identified interests, preferences and historicalactivity.

FIG. 1 shows a data flow diagram illustrating example aspects of someembodiments of the EECP. It is to be understood the processesillustrated in FIG. 1 are not restrictive and may be customized based onthe requirements of various administrative users including, and notlimited to, merchant administrators, account administrators, productheads, even administrators, and/or the like. As shown in FIG. 1, a usermay provide user login information 105 and receive processed calendaringinformation 170 generated based on the user login information 110-160.In some embodiments a user's profile may be retrieved 110 from a userdatabase 106 b structured to maintain user profile information and usersegmentation information. Also, as shown, events may be accessed by anevent server 106 where events may be updated and associated with auser's login data and user profile 135. For example, a user's profilemay indicate an interest in football games, an event server may collectall relevant football game events. In some embodiments, the collectedevents may be scored according to various degrees of relevance. Forexample, an event may be more highly scored than another event becauseit falls within an opening in a user's calendar where no events (or lowpriority, tentative events) are scheduled. In another example, an eventmay be more highly ranked than another event if said event is associatedwith more than one user profile interest. FIG. 1 also shows thatcalendar conflicts 150, once identified, may be resolved according torelevant events and a user's profile 155. Once resolved, in someembodiments, an updated calendar may be generated to be populated withthe various calendar conflict resolutions 160.

FIG. 2 is a logic flow diagram illustrating an embodiment of the EECP.As shown in FIG. 2, user login data may effectuate retrieval of eventrelated information that may be curated and ordered according to aninterest/preference relevancy to the user 203-212. In some embodiments,calendar conflicts may be weighed, and so may calendar conflictresolutions 217. Ultimately, in some embodiments, a number of calendarsmay be generated based on the user's profile, user login data, retrievedevents, and weighted calendar conflict resolutions 218-219.

FIG. 3 is a logic flow diagram illustrating an embodiment of the EECP.FIG. 3 shows an exemplary process by which event data may be gatheredand scored according to a user's login data. In some embodiments aplurality of scoring parameters may be derived 303, 305 from historicalstatistical analysis comprising, but not limited to, user segmentationtrends and historical and real-time event data (i.e., event turnouts,user ratings, etc.).

In another embodiment, the EECP may be configured to provide recommendedaction options based on populated calendars.

In another embodiment, the EECP may be configured to search and collectevent information. In such an embodiment the EECP may be configured toorganize event information according to an assortment of variables(e.g., event type, event location, event audience, event duration, eventfrequency, event “freshness”, source “freshness,” etc.), wherein saidvariables are used to structure events (past, present and future) for“global’ event storage and maintenance and/or for “local,” userspecific, maintenance and usage.

In one embodiment, the EECP may be configured to include Event Database,an Event Source Database, an Event Retrieval Component, Event CollectionComponent, Event Assignment Component, User Profiles, User Calendars,Calendar Export Component, User Databases, and/or the like.

In one embodiment, the EECP may be configured to process interests andpreferences and push events associated with processed interests andpreferences to various implementations (e.g., user calendars, etc.).

In one embodiment the EECP may be configured to populate variousimplementations (e.g., calendars, email summaries, micro bloggingstreams, etc.) with events based on identified interests, and may beable to do so in real-time.

In one embodiment the EECP may be configured to allow user specificediting of interests and preferences.

Some implementations of the EECP may be configured share viewership andcontent with a diversity of internal and external users.

Some implementations of the EECP may be configured to export processeddata, and/or sustain access of processed data to third party calendaringand event applications (e.g., Outlook, Google Calendar, iCal, etc.).

Some embodiments of the EECP may be configured to provide users with adiversity of sharing/viewing preferences/permissions, in suchembodiments user may be able to edit/modify a collection of saidpreferences/permissions.

Some embodiments of the EECP may be configured to provide users theability to subscribe to and/or follow the development/maintenance of aother user's EECP implementations (e.g., calendars, RSS feeds, emailnewsletters, etc.).

Some embodiments of the EECP may be configured to process future events(e.g., Eventuals, Eventual Events, etc.) associated with a user's basedupon the user's defined interests/preferences, EECP activity history,and/or the like.

Some embodiments of the EECP may be configured to function acrossvarious third-party platforms including web applications, local mobileapplications, and/or the like.

In one embodiment the EECP may be configured to process date informationof articles, blog posts, tweets, etc and determine a calendar category,preference class, event, appropriate user assignment, and/or the like.Such an embodiment may be able to parse the article of less importantdata and transport the relevant data, or snippet of data to a descriptorof a determined event entry.

One embodiment of the EECP may be configured to provide a one-clickevent bookmarking implementation (e.g., Eventually Button, EventualButton, etc.). In such an embodiment the bookmarking implementation mayoperate as a web widget and may maintain a connection to an embodimentof the EECP. For example, the bookmarking implementation mayadd/transmit event information to an EECP embodiment for processingand/or storage. Further, the bookmarking tool may instantly process theadjoining web page(s) for event related information (e.g., undefined,pre-defined, etc.) and transmit the aggregate to an EECP embodiment forfurther processing, storage and/or User Profile assignment.

In one embodiment the EECP may be configured to generate and update anevent source database which may include comprehensive event sourceinformation comprising, as an example, ticketing sites (e.g.,Ticketmaster, stubhub.com, etc.), events sites (e.g., upcoming.com,www.nycgo.com, timeout.com, etc.), entertainment venue calendars/sites(e.g., www.boweryballroom.com, etc.), social calendars, academiccalendars (e.g., student-related events and activities, lectures, etc.),sports listings, sporting calendars/sites (e.g., nba.com, nfl.com,etc.), non-public sources (e.g., mailing lists, shared group calendars,employer calendars), historical collections (e.g., user's past events,attended parties, birthdays, etc.), TV listings (e.g., TV guidelistings, cable TV listings, etc.), comment sections of blogs andvideos, and/or the like.

In some embodiments and implementations of the EECP an event source mayinclude digital data sources comprising event information. Asnon-limiting examples, websites, web pages, digital assets, socialnetworking sources, micro blogging services, RSS feeds, SMS services,etc.

In one embodiment the EECP may be configured to process data and updatea user database. In such an embodiment a user database may be structuredto include user information, user profile information, and/or the like.

In one embodiment, a user profile may be directly accessible andeditable by a user. In one embodiment user profiles may include securityfeatures, for example a user facing implementation of the EECP mayprovide a user profile accessibly by a user once the user has loggedinto a hosting EECP embodiment. In some embodiments and implementation auser profile may include menu interfaces and data organized according toUser Information (e.g., Name, Email Address, Location, Passwordinformation, etc.), User Interests and Preferences, Privacy and SharingPermissions, Contacts, Eventual Friends, Followed Eventual Calendars,Export, Import and Sync, and/or the like.

In some embodiments a user event database may include a user's storedevents, organized/structured according to a user's user profileInterests and preferences.

In some embodiments the EECP may be configured to provide User CreatedProfiles/Calendars. In such embodiments users may be able to createprofiles comprising interests and preferences for hypothetical people,wherein hypothetical people have been crafted according user definedprofiles via the EECP. As a non-limiting example, a husband may be ableto create an Eventual Calendar based on a profile he created based onhis wife and her interests and preferences.

In some embodiments the EECP may be configured to provide UserCalendars, which may include an editable graphical user interface thatmay visualize a user's Event Database, and/or the like.

In some embodiments the EECP may be configured to convert and/orgenerate User Calendars into iCalendar format (e.g., .ical, .ics, .ifb,.icalendar, etc.).

In some embodiments the EECP may be configured to convert a UserCalendar into a variety of third application files types as defined byspecific calendar APIs (e.g., iCal, Outlook, Google Calendar, etc).

In some embodiments the EECP may be configured to import calendarinformation from a variety of third application files types as definedby specific calendar APIs (e.g., iCal, Outlook, Google Calendar, etc).For example, a user may be able to navigate a plurality of iCalcalendars and select a variety of calendars to import in an EECP UserCalendar. In such an example a plurality of iCal calendars may beaggregated, organized and presented by an embodiment of the EECP.

In one embodiments the EECP may be configured to operate online as a webapplication, via a mobile device as a web application, via a mobiledevice as a local mobile application (e.g., Android app, iPhoneapplication, etc.), and/or the like.

EECP Controller

FIG. 4 illustrates inventive aspects of a EECP controller 401 in a blockdiagram. In this embodiment, the EECP controller 401 may serve toaggregate, process, store, search, serve, identify, instruct, generate,match, and/or facilitate interactions with a computer through eventsearching, event collection, and event relationship generationtechnologies, and/or other related data.

Typically, users, which may be people and/or other systems, may engageinformation technology systems (e.g., computers) to facilitateinformation processing. In turn, computers employ processors to processinformation; such processors 403 may be referred to as centralprocessing units (CPU). One form of processor is referred to as amicroprocessor. CPUs use communicative circuits to pass binary encodedsignals acting as instructions to enable various operations. Theseinstructions may be operational and/or data instructions containingand/or referencing other instructions and data in various processoraccessible and operable areas of memory 429 (e.g., registers, cachememory, random access memory, etc.). Such communicative instructions maybe stored and/or transmitted in batches (e.g., batches of instructions)as programs and/or data components to facilitate desired operations.These stored instruction codes, e.g., programs, may engage the CPUcircuit components and other motherboard and/or system components toperform desired operations. One type of program is a computer operatingsystem, which, may be executed by CPU on a computer; the operatingsystem enables and facilitates users to access and operate computerinformation technology and resources. Some resources that may beemployed in information technology systems include: input and outputmechanisms through which data may pass into and out of a computer;memory storage into which data may be saved; and processors by whichinformation may be processed. These information technology systems maybe used to collect data for later retrieval, analysis, and manipulation,which may be facilitated through a database program. These informationtechnology systems provide interfaces that allow users to access andoperate various system components.

In one embodiment, the EECP controller 401 may be connected to and/orcommunicate with entities such as, but not limited to: one or more usersfrom user input devices 411; peripheral devices 412; an optionalcryptographic processor device 428; and/or a communications network 413.

Networks are commonly thought to comprise the interconnection andinteroperation of clients, servers, and intermediary nodes in a graphtopology. It should be noted that the term “server” as used throughoutthis application refers generally to a computer, other device, program,or combination thereof that processes and responds to the requests ofremote users across a communications network. Servers serve theirinformation to requesting “clients.” The term “client” as used hereinrefers generally to a computer, program, other device, user and/orcombination thereof that is capable of processing and making requestsand obtaining and processing any responses from servers across acommunications network. A computer, other device, program, orcombination thereof that facilitates, processes information andrequests, and/or furthers the passage of information from a source userto a destination user is commonly referred to as a “node.” Networks aregenerally thought to facilitate the transfer of information from sourcepoints to destinations. A node specifically tasked with furthering thepassage of information from a source to a destination is commonly calleda “router.” There are many forms of networks such as Local Area Networks(LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks(WLANs), etc. For example, the Internet is generally accepted as beingan interconnection of a multitude of networks whereby remote clients andservers may access and interoperate with one another.

The EECP controller 401 may be based on computer systems that maycomprise, but are not limited to, components such as: a computersystemization 402 connected to memory 429.

Computer Systemization

A computer systemization 402 may comprise a clock 430, centralprocessing unit (“CPU(s)” and/or “processor(s)” (these terms are usedinterchangeable throughout the disclosure unless noted to the contrary))403, a memory 429 (e.g., a read only memory (ROM) 406, a random accessmemory (RAM) 405, etc.), and/or an interface bus 407, and mostfrequently, although not necessarily, are all interconnected and/orcommunicating through a system bus 404 on one or more (mother)board(s)402 having conductive and/or otherwise transportive circuit pathwaysthrough which instructions (e.g., binary encoded signals) may travel toeffect communications, operations, storage, etc. Optionally, thecomputer systemization may be connected to an internal power source 486.Optionally, a cryptographic processor 426 may be connected to the systembus. The system clock typically has a crystal oscillator and generates abase signal through the computer systemization's circuit pathways. Theclock is typically coupled to the system bus and various clockmultipliers that will increase or decrease the base operating frequencyfor other components interconnected in the computer systemization. Theclock and various components in a computer systemization drive signalsembodying information throughout the system. Such transmission andreception of instructions embodying information throughout a computersystemization may be commonly referred to as communications. Thesecommunicative instructions may further be transmitted, received, and thecause of return and/or reply communications beyond the instant computersystemization to: communications networks, input devices, other computersystemizations, peripheral devices, and/or the like. Of course, any ofthe above components may be connected directly to one another, connectedto the CPU, and/or organized in numerous variations employed asexemplified by various computer systems.

The CPU comprises at least one high-speed data processor adequate toexecute program components for executing user and/or system-generatedrequests. Often, the processors themselves will incorporate variousspecialized processing units, such as, but not limited to: integratedsystem (bus) controllers, memory management control units, floatingpoint units, and even specialized processing sub-units like graphicsprocessing units, digital signal processing units, and/or the like.Additionally, processors may include internal fast access addressablememory, and be capable of mapping and addressing memory 529 beyond theprocessor itself; internal memory may include, but is not limited to:fast registers, various levels of cache memory (e.g., level 1, 2, 3,etc.), RAM, etc. The processor may access this memory through the use ofa memory address space that is accessible via instruction address, whichthe processor can construct and decode allowing it to access a circuitpath to a specific memory address space having a memory state. The CPUmay be a microprocessor such as: AMD's Athlon, Duron and/or Opteron;ARM's application, embedded and secure processors; IBM and/or Motorola'sDragonBall and PowerPC; IBM's and Sony's Cell processor; Intel'sCeleron, Core (2) Duo, Itanium, Pentium, Xeon, and/or XScale; and/or thelike processor(s). The CPU interacts with memory through instructionpassing through conductive and/or transportive conduits (e.g., (printed)electronic and/or optic circuits) to execute stored instructions (i.e.,program code) according to conventional data processing techniques. Suchinstruction passing facilitates communication within the EECP controllerand beyond through various interfaces. Should processing requirementsdictate a greater amount speed and/or capacity, distributed processors(e.g., Distributed EECP), mainframe, multi-core, parallel, and/orsuper-computer architectures may similarly be employed. Alternatively,should deployment requirements dictate greater portability, smallerPersonal Digital Assistants (PDAs) may be employed.

Depending on the particular implementation, features of the EECP may beachieved by implementing a microcontroller such as CAST's R8051XC2microcontroller; Intel's MCS 51 (i.e., 8051 microcontroller); and/or thelike. Also, to implement certain features of the EECP, some featureimplementations may rely on embedded components, such as:Application-Specific Integrated Circuit (“ASIC”), Digital SignalProcessing (“DSP”), Field Programmable Gate Array (“FPGA”), and/or thelike embedded technology. For example, any of the EECP componentcollection (distributed or otherwise) and/or features may be implementedvia the microprocessor and/or via embedded components; e.g., via ASIC,coprocessor, DSP, FPGA, and/or the like. Alternately, someimplementations of the EECP may be implemented with embedded componentsthat are configured and used to achieve a variety of features or signalprocessing.

Depending on the particular implementation, the embedded components mayinclude software solutions, hardware solutions, and/or some combinationof both hardware/software solutions. For example, EECP featuresdiscussed herein may be achieved through implementing FPGAs, which are asemiconductor devices containing programmable logic components called“logic blocks”, and programmable interconnects, such as the highperformance FPGA Virtex series and/or the low cost Spartan seriesmanufactured by Xilinx. Logic blocks and interconnects can be programmedby the customer or designer, after the FPGA is manufactured, toimplement any of the EECP features. A hierarchy of programmableinterconnects allow logic blocks to be interconnected as needed by theEECP system designer/administrator, somewhat like a one-chipprogrammable breadboard. An FPGA's logic blocks can be programmed toperform the function of basic logic gates such as AND, and XOR, or morecomplex combinational functions such as decoders or simple mathematicalfunctions. In most FPGAs, the logic blocks also include memory elements,which may be simple flip-flops or more complete blocks of memory. Insome circumstances, the EECP may be developed on regular FPGAs and thenmigrated into a fixed version that more resembles ASIC implementations.Alternate or coordinating implementations may migrate EECP controllerfeatures to a final ASIC instead of or in addition to FPGAs. Dependingon the implementation all of the aforementioned embedded components andmicroprocessors may be considered the “CPU” and/or “processor” for theEECP.

Power Source

The power source 486 may be of any standard form for powering smallelectronic circuit board devices such as the following power cells:alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium,solar cells, and/or the like. Other types of AC or DC power sources maybe used as well. In the case of solar cells, in one embodiment, the caseprovides an aperture through which the solar cell may capture photonicenergy. The power cell 486 is connected to at least one of theinterconnected subsequent components of the EECP thereby providing anelectric current to all subsequent components. In one example, the powersource 486 is connected to the system bus component 404. In analternative embodiment, an outside power source 486 is provided througha connection across the I/O 408 interface. For example, a USB and/orIEEE 1394 connection carries both data and power across the connectionand is therefore a suitable source of power.

Interface Adapters

Interface bus(ses) 407 may accept, connect, and/or communicate to anumber of interface adapters, conventionally although not necessarily inthe form of adapter cards, such as but not limited to: input outputinterfaces (I/O) 408, storage interfaces 409, network interfaces 410,and/or the like. Optionally, cryptographic processor interfaces 427similarly may be connected to the interface bus. The interface busprovides for the communications of interface adapters with one anotheras well as with other components of the computer systemization.Interface adapters are adapted for a compatible interface bus. Interfaceadapters conventionally connect to the interface bus via a slotarchitecture. Conventional slot architectures may be employed, such as,but not limited to: Accelerated Graphics Port (AGP), Card Bus,(Extended) Industry Standard Architecture ((E)ISA), Micro ChannelArchitecture (MCA), NuBus, Peripheral Component Interconnect (Extended)(PCI(X)), PCI Express, Personal Computer Memory Card InternationalAssociation (PCMCIA), and/or the like.

Storage interfaces 409 may accept, communicate, and/or connect to anumber of storage devices such as, but not limited to: storage devices414, removable disc devices, and/or the like. Storage interfaces mayemploy connection protocols such as, but not limited to: (Ultra)(Serial) Advanced Technology Attachment (Packet Interface) ((Ultra)(Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE),Institute of Electrical and Electronics Engineers (IEEE) 1394, fiberchannel, Small Computer Systems Interface (SCSI), Universal Serial Bus(USB), and/or the like.

Network interfaces 410 may accept, communicate, and/or connect to acommunications network 413. Through a communications network 413, theEECP controller is accessible through remote clients 433 b (e.g.,computers with web browsers) by users 433 a. Network interfaces mayemploy connection protocols such as, but not limited to: direct connect,Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or thelike), Token Ring, wireless connection such as IEEE 802.11a-x, and/orthe like. Should processing requirements dictate a greater amount speedand/or capacity, distributed network controllers (e.g., DistributedEECP), architectures may similarly be employed to pool, load balance,and/or otherwise increase the communicative bandwidth required by theEECP controller. A communications network may be any one and/or thecombination of the following: a direct interconnection; the Internet; aLocal Area Network (LAN); a Metropolitan Area Network (MAN); anOperating Missions as Nodes on the Internet (OMNI); a secured customconnection; a Wide Area Network (WAN); a wireless network (e.g.,employing protocols such as, but not limited to a Wireless ApplicationProtocol (WAP), I-mode, and/or the like); and/or the like. A networkinterface may be regarded as a specialized form of an input outputinterface. Further, multiple network interfaces 410 may be used toengage with various communications network types 413. For example,multiple network interfaces may be employed to allow for thecommunication over broadcast, multicast, and/or unicast networks.

Input Output interfaces (I/O) 408 may accept, communicate, and/orconnect to user input devices 411, peripheral devices 412, cryptographicprocessor devices 428, and/or the like. I/O may employ connectionprotocols such as, but not limited to: audio: analog, digital, monaural,RCA, stereo, and/or the like; data: Apple Desktop Bus (ADB), IEEE1394a-b, serial, universal serial bus (USB); infrared; joystick;keyboard; midi; optical; PC AT; PS/2; parallel; radio; video interface:Apple Desktop Connector (ADC), BNC, coaxial, component, composite,digital, Digital Visual Interface (DVI), high-definition multimediainterface (HDMI), RCA, RF antennae, S-Video, VGA, and/or the like;wireless: 802.11a/b/g/n/x, Bluetooth, code division multiple access(CDMA), global system for mobile communications (GSM), WiMax, etc.;and/or the like. One typical output device may include a video display,which typically comprises a Cathode Ray Tube (CRT) or Liquid CrystalDisplay (LCD) based monitor with an interface (e.g., DVI circuitry andcable) that accepts signals from a video interface, may be used. Thevideo interface composites information generated by a computersystemization and generates video signals based on the compositedinformation in a video memory frame. Another output device is atelevision set, which accepts signals from a video interface. Typically,the video interface provides the composited video information through avideo connection interface that accepts a video display interface (e.g.,an RCA composite video connector accepting an RCA composite video cable;a DVI connector accepting a DVI display cable, etc.).

User input devices 411 may be card readers, dongles, finger printreaders, gloves, graphics tablets, joysticks, keyboards, mouse (mice),remote controls, retina readers, trackballs, trackpads, and/or the like.

Peripheral devices 412 may be connected and/or communicate to I/O and/orother facilities of the like such as network interfaces, storageinterfaces, and/or the like. Peripheral devices may be audio devices,cameras, dongles (e.g., for copy protection, ensuring securetransactions with a digital signature, and/or the like), externalprocessors (for added functionality), goggles, microphones, monitors,network interfaces, printers, scanners, storage devices, video devices,video sources, visors, and/or the like.

It should be noted that although user input devices and peripheraldevices may be employed, the EECP controller may be embodied as anembedded, dedicated, and/or monitor-less (i.e., headless) device,wherein access would be provided over a network interface connection.

Cryptographic units such as, but not limited to, microcontrollers,processors 426, interfaces 427, and/or devices 428 may be attached,and/or communicate with the EECP controller. A MC68HC16 microcontroller,manufactured by Motorola Inc., may be used for and/or withincryptographic units. The MC68HC16 microcontroller utilizes a 16-bitmultiply-and-accumulate instruction in the 16 MHz configuration andrequires less than one second to perform a 512-bit RSA private keyoperation. Cryptographic units support the authentication ofcommunications from interacting agents, as well as allowing foranonymous transactions. Cryptographic units may also be configured aspart of CPU. Equivalent microcontrollers and/or processors may also beused. Other commercially available specialized cryptographic processorsinclude: the Broadcom's CryptoNetX and other Security Processors;nCipher's nShield, SafeNet's Luna PCI (e.g., 7100) series; SemaphoreCommunications' 40 MHz Roadrunner 184; Sun's Cryptographic Accelerators(e.g., Accelerator 6000 PCIe Board, Accelerator 500 Daughtercard); ViaNano Processor (e.g., L2100, L2200, U2400) line, which is capable ofperforming 500+MB/s of cryptographic instructions; VLSI Technology's 33MHz 6868; and/or the like.

Memory

Generally, any mechanization and/or embodiment allowing a processor toaffect the storage and/or retrieval of information is regarded as memory429. However, memory is a fungible technology and resource, thus, anynumber of memory embodiments may be employed in lieu of or in concertwith one another. It is to be understood that the EECP controller and/ora computer systemization may employ various forms of memory 429. Forexample, a computer systemization may be configured wherein thefunctionality of on-chip CPU memory (e.g., registers), RAM, ROM, and anyother storage devices are provided by a paper punch tape or paper punchcard mechanism; of course such an embodiment would result in anextremely slow rate of operation. In a typical configuration, memory 429will include ROM 406, RAM 405, and a storage device 414. A storagedevice 414 may be any conventional computer system storage. Storagedevices may include a drum; a (fixed and/or removable) magnetic diskdrive; a magneto-optical drive; an optical drive (i.e., Blueray, CDROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); anarray of devices (e.g., Redundant Array of Independent Disks (RAID));solid state memory devices (USB memory, solid state drives (SSD), etc.);other processor-readable storage mediums; and/or other devices of thelike. Thus, a computer systemization generally requires and makes use ofmemory.

Component Collection

The memory 429 may contain a collection of program and/or databasecomponents and/or data such as, but not limited to: operating systemcomponent(s) 415 (operating system); information server component(s) 416(information server); user interface component(s) 417 (user interface);Web browser component(s) 418 (Web browser); database(s) 419; mail servercomponent(s) 421; mail client component(s) 422; cryptographic servercomponent(s) 420 (cryptographic server); the EECP component(s) 435;and/or the like (i.e., collectively a component collection). Thesecomponents may be stored and accessed from the storage devices and/orfrom storage devices accessible through an interface bus. Althoughnon-conventional program components such as those in the componentcollection, typically, are stored in a local storage device 414, theymay also be loaded and/or stored in memory such as: peripheral devices,RAM, remote storage facilities through a communications network, ROM,various forms of memory, and/or the like.

Operating System

The operating system component 415 is an executable program componentfacilitating the operation of the EECP controller. Typically, theoperating system facilitates access of I/O, network interfaces,peripheral devices, storage devices, and/or the like. The operatingsystem may be a highly fault tolerant, scalable, and secure system suchas: Apple Macintosh OS X (Server); AT&T Plan 9; Be OS; Unix andUnix-like system distributions (such as AT&T's UNIX; Berkley SoftwareDistribution (BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/orthe like; Linux distributions such as Red Hat, Ubuntu, and/or the like);and/or the like operating systems. However, more limited and/or lesssecure operating systems also may be employed such as Apple MacintoshOS, IBM OS/2, Microsoft DOS, Microsoft Windows2000/2003/3.1/95/98/CE/Millenium/NT/Vista/XP (Server), Palm OS, and/orthe like. An operating system may communicate to and/or with othercomponents in a component collection, including itself, and/or the like.Most frequently, the operating system communicates with other programcomponents, user interfaces, and/or the like. For example, the operatingsystem may contain, communicate, generate, obtain, and/or provideprogram component, system, user, and/or data communications, requests,and/or responses. The operating system, once executed by the CPU, mayenable the interaction with communications networks, data, I/O,peripheral devices, program components, memory, user input devices,and/or the like. The operating system may provide communicationsprotocols that allow the EECP controller to communicate with otherentities through a communications network 413. Various communicationprotocols may be used by the EECP controller as a subcarrier transportmechanism for interaction, such as, but not limited to: multicast,TCP/IP, UDP, unicast, and/or the like.

Information Server

An information server component 416 is a stored program component thatis executed by a CPU. The information server may be a conventionalInternet information server such as, but not limited to Apache SoftwareFoundation's Apache, Microsoft's Internet Information Server, and/or thelike. The information server may allow for the execution of programcomponents through facilities such as Active Server Page (ASP), ActiveX,(ANSI) (Objective-) C (++), C# and/or .NET, Common Gateway Interface(CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH,Java, JavaScript, Practical Extraction Report Language (PERL), HypertextPre-Processor (PHP), pipes, Python, wireless application protocol (WAP),WebObjects, and/or the like. The information server may support securecommunications protocols such as, but not limited to, File TransferProtocol (FTP); HyperText Transfer Protocol (HTITP); Secure HypertextTransfer Protocol (HTTPS), Secure Socket Layer (SSL), messagingprotocols (e.g., America Online (AOL) Instant Messenger (AIM),Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), MicrosoftNetwork (MSN) Messenger Service, Presence and Instant Messaging Protocol(PRIM), Internet Engineering Task Force's (IETF's) Session InitiationProtocol (SIP), SIP for Instant Messaging and Presence LeveragingExtensions (SIMPLE), open XML-based Extensible Messaging and PresenceProtocol (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) InstantMessaging and Presence Service (IMPS)), Yahoo! Instant MessengerService, and/or the like. The information server provides results in theform of Web pages to Web browsers, and allows for the manipulatedgeneration of the Web pages through interaction with other programcomponents. After a Domain Name System (DNS) resolution portion of anHTTP request is resolved to a particular information server, theinformation server resolves requests for information at specifiedlocations on the EECP controller based on the remainder of the HTITPrequest. For example, a request such ashttp://123.124.125.126/myInformation.html might have the IP portion ofthe request “123.124.125.126” resolved by a DNS server to an informationserver at that IP address; that information server might in turn furtherparse the http request for the “/myInformation.html” portion of therequest and resolve it to a location in memory containing theinformation “myInformation.html.” Additionally, other informationserving protocols may be employed across various ports, e.g., FTPcommunications across port 21, and/or the like. An information servermay communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Mostfrequently, the information server communicates with the EECP database419, operating systems, other program components, user interfaces, Webbrowsers, and/or the like.

Access to the EECP database may be achieved through a number of databasebridge mechanisms such as through scripting languages as enumeratedbelow (e.g., CGI) and through inter-application communication channelsas enumerated below (e.g., CORBA, WebObjects, etc.). Any data requeststhrough a Web browser are parsed through the bridge mechanism intoappropriate grammars as required by the EECP. In one embodiment, theinformation server would provide a Web form accessible by a Web browser.Entries made into supplied fields in the Web form are tagged as havingbeen entered into the particular fields, and parsed as such. The enteredterms are then passed along with the field tags, which act to instructthe parser to generate queries directed to appropriate tables and/orfields. In one embodiment, the parser may generate queries in standardSQL by instantiating a search string with the proper join/selectcommands based on the tagged text entries, wherein the resulting commandis provided over the bridge mechanism to the EECP as a query. Upongenerating query results from the query, the results are passed over thebridge mechanism, and may be parsed for formatting and generation of anew results Web page by the bridge mechanism. Such a new results Webpage is then provided to the information server, which may supply it tothe requesting Web browser.

Also, an information server may contain, communicate, generate, obtain,and/or provide program component, system, user, and/or datacommunications, requests, and/or responses.

User Interface

The function of computer interfaces in some respects is similar toautomobile operation interfaces. Automobile operation interface elementssuch as steering wheels, gearshifts, and speedometers facilitate theaccess, operation, and display of automobile resources, functionality,and status. Computer interaction interface elements such as check boxes,cursors, menus, scrollers, and windows (collectively and commonlyreferred to as widgets) similarly facilitate the access, operation, anddisplay of data and computer hardware and operating system resources,functionality, and status. Operation interfaces are commonly called userinterfaces. Graphical user interfaces (GUIs) such as the Apple MacintoshOperating System's Aqua, IBM's OS/2, Microsoft's Windows2000/2003/3.1/95/98/CE/Millenium/NT/XP/Vista/7 (i.e., Aero), Unix'sX-Windows (e.g., which may include additional Unix graphic interfacelibraries and layers such as K Desktop Environment (KDE), mythTV and GNUNetwork Object Model Environment (GNOME)), web interface libraries(e.g., ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, etc. interfacelibraries such as, but not limited to, Dojo, jQuery(UI), MooTools,Prototype, scriptaculo.us, SWFObject, Yahoo! User Interface, any ofwhich may be used and) provide a baseline and means of accessing anddisplaying information graphically to users.

A user interface component 417 is a stored program component that isexecuted by a CPU. The user interface may be a conventional graphic userinterface as provided by, with, and/or atop operating systems and/oroperating environments such as already discussed. The user interface mayallow for the display, execution, interaction, manipulation, and/oroperation of program components and/or system facilities through textualand/or graphical facilities. The user interface provides a facilitythrough which users may affect, interact, and/or operate a computersystem. A user interface may communicate to and/or with other componentsin a component collection, including itself, and/or facilities of thelike. Most frequently, the user interface communicates with operatingsystems, other program components, and/or the like. The user interfacemay contain, communicate, generate, obtain, and/or provide programcomponent, system, user, and/or data communications, requests, and/orresponses.

Web Browser

A Web browser component 418 is a stored program component that isexecuted by a CPU. The Web browser may be a conventional hypertextviewing application such as Microsoft Internet Explorer or NetscapeNavigator. Secure Web browsing may be supplied with 128 bit (or greater)encryption by way of HTTPS, SSL, and/or the like. Web browsers allowingfor the execution of program components through facilities such asActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-inAPIs (e.g., FireFox, Safari Plug-in, and/or the like APIs), and/or thelike. Web browsers and like information access tools may be integratedinto PDAs, cellular telephones, and/or other mobile devices. A Webbrowser may communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Mostfrequently, the Web browser communicates with information servers,operating systems, integrated program components (e.g., plug-ins),and/or the like; e.g., it may contain, communicate, generate, obtain,and/or provide program component, system, user, and/or datacommunications, requests, and/or responses. Of course, in place of a Webbrowser and information server, a combined application may be developedto perform similar functions of both. The combined application wouldsimilarly affect the obtaining and the provision of information tousers, user agents, and/or the like from the EECP enabled nodes. Thecombined application may be nugatory on systems employing standard Webbrowsers.

Mail Server

A mail server component 421 is a stored program component that isexecuted by a CPU 403. The mail server may be a conventional Internetmail server such as, but not limited to sendmail, Microsoft Exchange,and/or the like. The mail server may allow for the execution of programcomponents through facilities such as ASP, ActiveX, (ANSI) (Objective-)C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes,Python, WebObjects, and/or the like. The mail server may supportcommunications protocols such as, but not limited to: Internet messageaccess protocol (IMAP), Messaging Application Programming Interface(MAPI)/Microsoft Exchange, post office protocol (POP3), simple mailtransfer protocol (SMTP), and/or the like. The mail server can route,forward, and process incoming and outgoing mail messages that have beensent, relayed and/or otherwise traversing through and/or to the EECP.

Access to the EECP mail may be achieved through a number of APIs offeredby the individual Web server components and/or the operating system.

Also, a mail server may contain, communicate, generate, obtain, and/orprovide program component, system, user, and/or data communications,requests, information, and/or responses.

Mail Client

A mail client component 422 is a stored program component that isexecuted by a CPU 403. The mail client may be a conventional mailviewing application such as Apple Mail, Microsoft Entourage, MicrosoftOutlook, Microsoft Outlook Express, Mozilla, Thunderbird, and/or thelike. Mail clients may support a number of transfer protocols, such as:IMAP, Microsoft Exchange, POP3, SMTP, and/or the like. A mail client maycommunicate to and/or with other components in a component collection,including itself, and/or facilities of the like. Most frequently, themail client communicates with mail servers, operating systems, othermail clients, and/or the like; e.g., it may contain, communicate,generate, obtain, and/or provide program component, system, user, and/ordata communications, requests, information, and/or responses. Generally,the mail client provides a facility to compose and transmit electronicmail messages.

Cryptographic Server

A cryptographic server component 420 is a stored program component thatis executed by a CPU 403, cryptographic processor 426, cryptographicprocessor interface 427, cryptographic processor device 428, and/or thelike. Cryptographic processor interfaces will allow for expedition ofencryption and/or decryption requests by the cryptographic component;however, the cryptographic component, alternatively, may run on aconventional CPU. The cryptographic component allows for the encryptionand/or decryption of provided data. The cryptographic component allowsfor both symmetric and asymmetric (e.g., Pretty Good Protection (PGP))encryption and/or decryption. The cryptographic component may employcryptographic techniques such as, but not limited to: digitalcertificates (e.g., X.509 authentication framework), digital signatures,dual signatures, enveloping, password access protection, public keymanagement, and/or the like. The cryptographic component will facilitatenumerous (encryption and/or decryption) security protocols such as, butnot limited to: checksum, Data Encryption Standard (DES), EllipticalCurve Encryption (ECC), International Data Encryption Algorithm (IDEA),Message Digest 5 (MD5, which is a one way hash function), passwords,Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption andauthentication system that uses an algorithm developed in 1977 by RonRivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA),Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS),and/or the like. Employing such encryption security protocols, the EECPmay encrypt all incoming and/or outgoing communications and may serve asnode within a virtual private network (VPN) with a wider communicationsnetwork. The cryptographic component facilitates the process of“security authorization” whereby access to a resource is inhibited by asecurity protocol wherein the cryptographic component effects authorizedaccess to the secured resource. In addition, the cryptographic componentmay provide unique identifiers of content, e.g., employing and MD5 hashto obtain a unique signature for an digital audio file. A cryptographiccomponent may communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Thecryptographic component supports encryption schemes allowing for thesecure transmission of information across a communications network toenable the EECP component to engage in secure transactions if sodesired. The cryptographic component facilitates the secure accessing ofresources on the EECP and facilitates the access of secured resources onremote systems; i.e., it may act as a client and/or server of securedresources. Most frequently, the cryptographic component communicateswith information servers, operating systems, other program components,and/or the like. The cryptographic component may contain, communicate,generate, obtain, and/or provide program component, system, user, and/ordata communications, requests, and/or responses.

The EECP Database

The EECP database component 419 may be embodied in a database and itsstored data. The database is a stored program component, which isexecuted by the CPU; the stored program component portion configuringthe CPU to process the stored data. The database may be a conventional,fault tolerant, relational, scalable, secure database such as Oracle orSybase. Relational databases are an extension of a flat file. Relationaldatabases consist of a series of related tables. The tables areinterconnected via a key field. Use of the key field allows thecombination of the tables by indexing against the key field; i.e., thekey fields act as dimensional pivot points for combining informationfrom various tables. Relationships generally identify links maintainedbetween tables by matching primary keys. Primary keys represent fieldsthat uniquely identify the rows of a table in a relational database.More precisely, they uniquely identify rows of a table on the “one” sideof a one-to-many relationship.

Alternatively, the EECP database may be implemented using variousstandard data-structures, such as an array, hash, (linked) list, struct,structured text file (e.g., XML), table, and/or the like. Suchdata-structures may be stored in memory and/or in (structured) files. Inanother alternative, an object-oriented database may be used, such asFrontier, ObjectStore, Poet, Zope, and/or the like. Object databases caninclude a number of object collections that are grouped and/or linkedtogether by common attributes; they may be related to other objectcollections by some common attributes. Object-oriented databases performsimilarly to relational databases with the exception that objects arenot just pieces of data but may have other types of functionalityencapsulated within a given object. If the EECP database is implementedas a data-structure, the use of the EECP database 419 may be integratedinto another component such as the EECP component 435. Also, thedatabase may be implemented as a mix of data structures, objects, andrelational structures. Databases may be consolidated and/or distributedin countless variations through standard data processing techniques.Portions of databases, e.g., tables, may be exported and/or imported andthus decentralized and/or integrated.

In one embodiment, the database component 419 includes several tables419 a-j. A User table 419 a includes fields such as, but not limited to:a user_ID, user_email, user_calendar1, user_calendar2, user_age,user_preference1, user_preference2, user_interest1, user_interest2,and/or the like. The user table may support and/or track multiple entityaccounts on a EECP. An Event table 419 b includes fields such as, butnot limited to: event_ID, event_type, event_class, event_duration,event_rank, event_rating, event_source, event_time, event_location,event_address1, event_zip, event_email, event_telephone, event_link,event_descrip, and/or the like. An Event Source table 419 e includesfields such as, but not limited to: eventsource_ID, eventsource_type,eventsource_class, eventsource_rank, eventsource_rating,eventsource_updatefrequency, eventsource_link, eventsource_link2,eventsource_email, eventsource_dataformat, and/or the like. A Calendartable 419 d includes fields such as, but not limited to: calendar_ID,calendar_type, calendar_class, calendar_preference2,calendar_preference2, calendar_interest1, calendar_interest2, and/or thelike. An Interests-Preferences table 419 e includes fields such as, butnot limited to: interest_ID, preference_ID, interest_type,preference_type, interest_genre, preference_genre, interest_source,preference_source, interest_rank, preference_rank, and/or the like. AUser Segmentations table 419 f includes fields such as, but not limitedto: segmentation_ID, preference_ID, user_ID, interest_ID, event_ID,and/or the like. A Conflicts table 419 g includes fields such as, butnot limited to: conflict_ID, user_ID, score_value, event_ID, event_type,and/or the like. An Offers table 419 h includes fields such as, but notlimited to: offer_ID, conflict_ID, user_ID, interest_ID, event_ID,offer_type, offer_value, and/or the like. A Product table 419 i includesfields such as, but not limited to: product_ID, product_type, event_ID,event_type, interest_ID, and/or the like. An Activity table 419 jincludes fields such as, but not limited to: activity_ID, activity_type,event_ID, user_ID, and/or the like.

In one embodiment, the EECP database may interact with other databasesystems. For example, employing a distributed database system, queriesand data access by search EECP component may treat the combination ofthe EECP database, an integrated data security layer database as asingle database entity.

In one embodiment, user programs may contain various user interfaceprimitives, which may serve to update the EECP. Also, various accountsmay require custom database tables depending upon the environments andthe types of clients the EECP may need to serve. It should be noted thatany unique fields may be designated as a key field throughout. In analternative embodiment, these tables have been decentralized into theirown databases and their respective database controllers (i.e.,individual database controllers for each of the above tables). Employingstandard data processing techniques, one may further distribute thedatabases over several computer systemizations and/or storage devices.Similarly, configurations of the decentralized database controllers maybe varied by consolidating and/or distributing the various databasecomponents 419 a-d. The EECP may be configured to keep track of varioussettings, inputs, and parameters via database controllers.

The EECP database may communicate to and/or with other components in acomponent collection, including itself, and/or facilities of the like.Most frequently, the EECP database communicates with the EECP component,other program components, and/or the like. The database may contain,retain, and provide information regarding other nodes and data.

The EECPs

The EECP component 435 is a stored program component that is executed bya CPU. In one embodiment, the EECP component incorporates any and/or allcombinations of the aspects of the EECP that was discussed in theprevious figures. As such, the EECP affects accessing, obtaining and theprovision of information, services, transactions, and/or the like acrossvarious communications networks.

The EECP component transforms inputs (e.g., user information, userprofile information, event information, import calendar information,etc.) via components (e.g., Event Calendaring Component 440, EventCollection and Scoring Component 441, Event Retreival Component, EventCollection Component, Event Assignment Component, Eventually Button,etc.) into outputs (e.g., user calendar, user calendar RSS feed, userprofile, etc.).

The EECP component enabling access of information between nodes may bedeveloped by employing standard development tools and languages such as,but not limited to: Apache components, Assembly, ActiveX, binaryexecutables, (ANSI) (Objective-) C (++), C# and/or .NET, databaseadapters, CGI scripts, Java, JavaScript, mapping tools, procedural andobject oriented development tools, PERL, PHP, Python, shell scripts, SQLcommands, web application server extensions, web developmentenvironments and libraries (e.g., Microsoft's ActiveX; Adobe AIR, FLEX &FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools;Prototype; script.aculo.us; Simple Object Access Protocol (SOAP);SWFObject; Yahoo! User Interface; and/or the like), WebObjects, and/orthe like. In one embodiment, the EECP server employs a cryptographicserver to encrypt and decrypt communications. The EECP component maycommunicate to and/or with other components in a component collection,including itself, and/or facilities of the like. Most frequently, theEECP component communicates with the EECP database, operating systems,other program components, and/or the like. The EECP may contain,communicate, generate, obtain, and/or provide program component, system,user, and/or data communications, requests, and/or responses.

Distributed VMPs

The structure and/or operation of any of the EECP node controllercomponents may be combined, consolidated, and/or distributed in anynumber of ways to facilitate development and/or deployment. Similarly,the component collection may be combined in any number of ways tofacilitate deployment and/or development. To accomplish this, one mayintegrate the components into a common code base or in a facility thatcan dynamically load the components on demand in an integrated fashion.

The component collection may be consolidated and/or distributed incountless variations through standard data processing and/or developmenttechniques. Multiple instances of any one of the program components inthe program component collection may be instantiated on a single node,and/or across numerous nodes to improve performance throughload-balancing and/or data-processing techniques. Furthermore, singleinstances may also be distributed across multiple controllers and/orstorage devices; e.g., databases. All program component instances andcontrollers working in concert may do so through standard dataprocessing communication techniques.

The configuration of the EECP controller will depend on the context ofsystem deployment. Factors such as, but not limited to, the budget,capacity, location, and/or use of the underlying hardware resources mayaffect deployment requirements and configuration. Regardless of if theconfiguration results in more consolidated and/or integrated programcomponents, results in a more distributed series of program components,and/or results in some combination between a consolidated anddistributed configuration, data may be communicated, obtained, and/orprovided. Instances of components consolidated into a common code basefrom the program component collection may communicate, obtain, and/orprovide data. This may be accomplished through intra-application dataprocessing communication techniques such as, but not limited to: datareferencing (e.g., pointers), internal messaging, object instancevariable communication, shared memory space, variable passing, and/orthe like.

If component collection components are discrete, separate, and/orexternal to one another, then communicating, obtaining, and/or providingdata with and/or to other component components may be accomplishedthrough inter-application data processing communication techniques suchas, but not limited to: Application Program Interfaces (API) informationpassage; (distributed) Component Object Model ((D)COM), (Distributed)Object Linking and Embedding ((D)OLE), and/or the like), Common ObjectRequest Broker Architecture (CORBA), Jini local and remote applicationprogram interfaces, JavaScript Object Notation (JSON), Remote MethodInvocation (RMI), SOAP, process pipes, shared files, and/or the like.Messages sent between discrete component components forinter-application communication or within memory spaces of a singularcomponent for intra-application communication may be facilitated throughthe creation and parsing of a grammar. A grammar may be developed byusing development tools such as lex, yacc, XML, and/or the like, whichallow for grammar generation and parsing capabilities, which in turn mayform the basis of communication messages within and between components.

For example, a grammar may be arranged to recognize the tokens of anHTTP post command, e.g.:

-   -   w3c-post http:// . . . Value1

where Value1 is discerned as being a parameter because “http://” is partof the grammar syntax, and what follows is considered part of the postvalue. Similarly, with such a grammar, a variable “Value1” may beinserted into an “http://” post command and then sent. The grammarsyntax itself may be presented as structured data that is interpretedand/or otherwise used to generate the parsing mechanism (e.g., a syntaxdescription text file as processed by lex, yacc, etc.). Also, once theparsing mechanism is generated and/or instantiated, it itself mayprocess and/or parse structured data such as, but not limited to:character (e.g., tab) delineated text, HTML, structured text streams,XML, and/or the like structured data. In another embodiment,inter-application data processing protocols themselves may haveintegrated and/or readily available parsers (e.g., JSON, SOAP, and/orlike parsers) that may be employed to parse (e.g., communications) data.Further, the parsing grammar may be used beyond message parsing, but mayalso be used to parse: databases, data collections, data stores,structured data, and/or the like. Again, the desired configuration willdepend upon the context, environment, and requirements of systemdeployment.

For example, in some implementations, the EECP controller may beexecuting a PHP script implementing a Secure Sockets Layer (“SSL”)socket server via the information server, which listens to incomingcommunications on a server port to which a client may send data, e.g.,data encoded in JSON format. Upon identifying an incoming communication,the PHP script may read the incoming message from the client device,parse the received JSON-encoded text data to extract information fromthe JSON-encoded text data into PHP script variables, and store the data(e.g., client identifying information, etc.) and/or extractedinformation in a relational database accessible using the StructuredQuery Language (“SQL”). An exemplary listing, written substantially inthe form of PHP/SQL commands, to accept JSON-encoded input data from aclient device via a SSL connection, parse the data to extract variables,and store the data to a database, is provided below:

<?PHP header(‘Content-Type: text/plain’); // set ip address and port tolisten to for incoming data $address = ‘192.168.0.100’; $port = 255; //create a server-side SSL socket, listen for/accept incomingcommunication $sock = socket_create(AF_INET, SOCK_STREAM, 0);socket_bind($sock, $address, $port) or die(‘Could not bind to address’);socket_listen($sock); $client = socket_accept($sock); // read input datafrom client device in 1024 byte blocks until end of message do {  $input= “”;  $input = socket_read($client, 1024);  *data .= *input; }while($input != “”); // parse data to extract variables $obj =json_decode($data, true); // store input data in a databasemysql_connect(“201.408.185.132”,$DBserver,$password); // access databaseserver mysql_select(“CLIENT_DB.SQL”); // select database to appendmysql_query(“INSERT INTO UserTable (transmission) VALUES ($data)”); //add data to UserTable table in a CLIENT databasemysql_close(“CLIENT_DB.SQL”); // close connection to database ?>

Also, the following resources may be used to provide example embodimentsregarding SOAP parser implementation:

http://www.xav.com/perl/site/lib/SOAP/Parser.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.doc/referenceguide295.htmand other parser implementations:

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.doc/referenceguide259.htmall of which are hereby expressly incorporated by reference.

In order to address various issues and advance the art, the entirety ofthis application for APPARATUSES, METHODS AND SYSTEMS FOR AN EVENTUALEVENT CALENDERING PLATFORM (including the Cover Page, Title, Headings,Field, Background, Summary, Brief Description of the Drawings, DetailedDescription, Claims, Abstract, Figures, Appendices, and otherwise)shows, by way of illustration, various embodiments in which the claimedinnovations may be practiced. The advantages and features of theapplication are of a representative sample of embodiments only, and arenot exhaustive and/or exclusive. They are presented only to assist inunderstanding and teach the claimed principles. It should be understoodthat they are not representative of all claimed innovations. As such,certain aspects of the disclosure have not been discussed herein. Thatalternate embodiments may not have been presented for a specific portionof the innovations or that further undescribed alternate embodiments maybe available for a portion is not to be considered a disclaimer of thosealternate embodiments. It will be appreciated that many of thoseundescribed embodiments incorporate the same principles of theinnovations and others are equivalent. Thus, it is to be understood thatother embodiments may be utilized and functional, logical, operational,organizational, structural and/or topological modifications may be madewithout departing from the scope and/or spirit of the disclosure. Assuch, all examples and/or embodiments are deemed to be non-limitingthroughout this disclosure. Also, no inference should be drawn regardingthose embodiments discussed herein relative to those not discussedherein other than it is as such for purposes of reducing space andrepetition. For instance, it is to be understood that the logical and/ortopological structure of any combination of any program components (acomponent collection), other components and/or any present feature setsas described in the figures and/or throughout are not limited to a fixedoperating order and/or arrangement, but rather, any disclosed order isexemplary and all equivalents, regardless of order, are contemplated bythe disclosure. Furthermore, it is to be understood that such featuresare not limited to serial execution, but rather, any number of threads,processes, services, servers, and/or the like that may executeasynchronously, concurrently, in parallel, simultaneously,synchronously, and/or the like are contemplated by the disclosure. Assuch, some of these features may be mutually contradictory, in that theycannot be simultaneously present in a single embodiment. Similarly, somefeatures are applicable to one aspect of the innovations, andinapplicable to others. In addition, the disclosure includes otherinnovations not presently claimed. Applicant reserves all rights inthose presently unclaimed innovations including the right to claim suchinnovations, file additional applications, continuations, continuationsin part, divisions, and/or the like thereof. As such, it should beunderstood that advantages, embodiments, examples, functional, features,logical, operational, organizational, structural, topological, and/orother aspects of the disclosure are not to be considered limitations onthe disclosure as defined by the claims or limitations on equivalents tothe claims. It is to be understood that, depending on the particularneeds and/or characteristics of a EECP individual and/or enterpriseuser, database configuration and/or relational model, data type, datatransmission and/or network framework, syntax structure, and/or thelike, various embodiments of the EECP, may be implemented that enable agreat deal of flexibility and customization. For example, aspects of theEECP may be adapted for product and service bidding. While variousembodiments and discussions of the EECP have been directed to virtualmarketplaces, however, it is to be understood that the embodimentsdescribed herein may be readily configured and/or customized for a widevariety of other applications and/or implementations.

What is claimed is:
 1. A non-transitory computer readable mediumcontaining instructions that when executed cause at least one processorto: receive user calendar event interest data and user-specifiedpreferences associated with a user; query calendar event data based onthe user calendar event interest data; score the query results based onthe user-specified preferences; a provide calendar event recommendationsto the user based on populated calendars of other users; receive one ormore selections associated with the scored query results from the user;generate one or more user calendar entries based on the one or morereceived selections; and provide the one or more generated user calendarentries to the user.
 2. The non-transitory computer readable medium ofclaim 1, further containing instructions that when executed cause the atleast one processor to: receive the calendar event data; and store thecalendar event data in a calendar event database.
 3. The non-transitorycomputer readable medium of claim 2, wherein the instructions that whenexecuted cause the at least one processor to store the calendar eventdata in the calendar event database comprise: instructions that whenexecuted cause the at least one processor to structure the calendarevent data according to one or more of event type, event frequency,event duration, event audience, event location, and event freshness. 4.The non-transitory computer readable medium of claim 2, wherein: theinstructions that when executed cause the at least one processor toreceive the calendar event data comprise: instructions that whenexecuted cause the at least one processor to receive the calendar eventdata from multiple sources; and the non-transitory computer readablemedium further contains instructions that when executed cause the atleast one processor to aggregate the calendar event data from themultiple sources into the calendar event database.
 5. The non-transitorycomputer readable medium of claim 1, wherein the instructions that whenexecuted cause the at least one processor to score the query resultscomprise: instructions that when executed cause the at least oneprocessor to score the query results based on historical statisticalanalysis and the user-specified preferences.
 6. The non-transitorycomputer readable medium of claim 1, wherein the one or more usercalendar entries comprise one or more calendar entries in iCalendarformat.
 7. The non-transitory computer readable medium of claim 1,wherein the instructions that when executed cause the at least oneprocessor to provide the one or more generated user calendar entries tothe user comprise at least one of: instructions that when executed causethe at least one processor to email the one or more generated usercalendar entries to the user; and instructions that when executed causethe at least one processor to transmit a Really Simple Syndication (RSS)feed that includes the one or more generated user calendar entries tothe user.
 8. The non-transitory computer readable medium of claim 1,wherein the instructions that when executed cause the at least oneprocessor to score the query results comprise: instructions that whenexecuted cause the at least one processor to score the query resultsbased on a number of user profile interests associated with an event. 9.The non-transitory computer readable medium of claim 1, furthercontaining instructions that when executed cause the at least oneprocessor to populate an email with events based on user profileinterests.
 10. The non-transitory computer readable medium of claim 1,further containing instructions that when executed cause the at leastone processor to process date information of a source to determine thecalendar event data.
 11. The non-transitory computer readable medium ofclaim 1, further containing instructions that when executed cause the atleast one processor to: receive a one-click selection to bookmark anevent; and process a web page associated with the event for informationrelated to the event.
 12. The non-transitory computer readable medium ofclaim 1, further containing instructions that when executed cause the atleast one processor to: a identify calendar conflicts; determinecalendar conflict resolutions; weigh the calendar conflict resolutions;and generate a number of calendars based at least in part on theweighted calendar conflict resolutions.
 13. The non-transitory computerreadable medium of claim 1, further containing instructions that whenexecuted cause the at least one processor to: parse data from a sourceto select only the data relevant to the calendar event data; andtransport a snippet of the data relevant to the calendar event data to adescriptor of a calendar event entry.
 14. A non-transitory computerreadable medium containing instructions that when executed cause atleast one processor to: receive user calendar event interest data anduser-specified preferences associated with a user; query calendar eventdata based on the user calendar event interest data; score the queryresults based on the user-specified preferences and event data, whereinthe event data includes event turnouts and user ratings; and receive oneor more selections associated with the scored query results from theuser.
 15. The non-transitory computer readable medium of claim 14,further containing instructions that when executed cause the at leastone processor to: receive the calendar event data; and store thecalendar event data in a calendar event database.
 16. The non-transitorycomputer readable medium of claim 15, wherein the instructions that whenexecuted cause the at least one processor to store the calendar eventdata in the calendar event database comprise: instructions that whenexecuted cause the at least one processor to structure the calendarevent data according to one or more of event type, event frequency,event duration, event audience, event location, and event freshness. 17.The non-transitory computer readable medium of claim 14, furthercontaining instructions that when executed cause the at least oneprocessor to: receive a profile comprising interests and preferences ofa hypothetical person from the user; and create a calendar for thehypothetical person based on the profile of the hypothetical person. 18.The non-transitory computer readable medium of claim 14, furthercontaining instructions that when executed cause the at least oneprocessor to: generate one or more user calendar entries based on theone or more received selections; and provide the one or more generateduser calendar entries to the user.
 19. A non-transitory computerreadable medium containing instructions that when executed cause atleast one processor to: receive user calendar event interest data anduser-specified preferences associated with a user; query calendar eventdata based on the user calendar event interest data; score the queryresults based on the user-specified preferences; identify calendarconflicts; determine calendar conflict resolutions; weigh the calendarconflict resolutions; and generate a number of calendars based at leastin part on the weighted calendar conflict resolutions.
 20. Thenon-transitory computer readable medium of claim 19, further containinginstructions that when executed cause the at least one processor to:receive the calendar event data; and store the calendar event data in acalendar event database.
 21. The non-transitory computer readable mediumof claim 20, wherein the instructions that when executed cause the atleast one processor to store the calendar event data in the calendarevent database comprise: instructions that when executed cause the atleast one processor to structure the calendar event data according toone or more of event type, event frequency, event duration, eventaudience, event location, and event freshness.
 22. The non-transitorycomputer readable medium of claim 19, wherein the instructions that whenexecuted cause the at least one processor to generate the number ofcalendars comprise: instructions that when executed cause the at leastone processor to generate the number of calendars based on user logindata, the user-specified preferences, and the query results.
 23. Thenon-transitory computer readable medium of claim 19, further containinginstructions that when executed cause the at least one processor to:generate one or more user calendar entries based on one or more receivedselections; and provide the one or more generated user calendar entriesto the user.